System and method of configuring power settings of an information handling system

ABSTRACT

In one or more embodiments, one or more systems, one or more methods, and/or one or more processes may execute a first information handling system (IHS) initialization executable of a first IHS initialization executable/operating system (OS) executable pair; execute a second OS executable of a second IHS initialization executable/OS executable pair via an OS context; determine, by the second OS executable, that at least one application has been installed on the IHS in addition to multiple applications that have already been installed on the IHS; determine, by the second OS executable, information associated with the at least one application and at least one of system information, power configuration information, status configuration information, and hardware information; and provide first information that recommends how to configure power utilization of the IHS and second information that recommends how not to configure power utilization of the IHS based at least on the determined information.

BACKGROUND Field of the Disclosure

This disclosure relates generally to information handling systems and more particularly to configuring power settings of an information handling system.

Description of the Related Art

As the value and use of information continues to increase, individuals and businesses seek additional ways to process and store information. One option available to users is information handling systems. An information handling system generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes thereby allowing users to take advantage of the value of the information. Because technology and information handling needs and requirements vary between different users or applications, information handling systems may also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information may be processed, stored, or communicated. The variations in information handling systems allow for information handling systems to be general or configured for a specific user or specific use such as financial transaction processing, airline reservations, enterprise data storage, or global communications. In addition, information handling systems may include a variety of hardware and software components that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems.

SUMMARY

In one or more embodiments, one or more systems, one or more methods, and/or one or more processes may execute, by at least one processor of an information handling system (IHS), at least a portion of information handling system firmware (IHSFW) from a first non-volatile memory medium of the IHS; may retrieve, from the first non-volatile memory medium, a first IHS initialization executable of a first IHS initialization executable/operating system (OS) executable pair; may execute, by the at least one processor, the first IHS initialization executable via an environment associated with the IHSFW; may retrieve, from the first non-volatile memory medium, a second IHS initialization executable of a second IHS initialization executable/OS executable pair; may execute, by the at least one processor, the second IHS initialization executable via the environment associated with the IHSFW; may execute, by the at least one processor, a second OS executable of a second IHS initialization executable/OS executable pair via an OS context of an operating system; may determine, by the second OS executable, that at least one application, executable via the OS context, has been installed on the IHS in addition to a plurality of applications, executable via the OS context, that have already been installed on the IHS; in response to determining that the at least one application has been installed on the IHS, may determine, by the second OS executable, information associated with the at least one application and at least one of system information associated with the IHS, power configuration information associated with the IHS, status configuration information associated with the IHS, and hardware information associated with the IHS; may receive, by the second OS executable, developed configuration information via a network; may provide, by the second OS executable, first information that recommends how to configure power utilization of the IHS and second information that recommends how not to configure power utilization of the IHS based at least on the developed configuration information, based at least on the information associated with the at least one application, and based at least on the at least one of system information associated with the IHS, power configuration information associated with the IHS, configuration information associated with the IHS, and hardware information associated with the IHS.

In one or more embodiments, the one or more systems, the one or more methods, and/or the one or more processes may further: register, by the first IHS initialization executable, a subroutine configured to store a plurality of addresses of a volatile memory medium of the IHS; copy, by the first IHS initialization executable, the first OS executable of the first IHS initialization executable/OS executable pair from the first non-volatile memory medium to the volatile memory medium; copy, by the second IHS initialization executable, the second OS executable from the first non-volatile memory medium to the volatile memory medium; call, by the second IHS initialization executable, the subroutine; store, by the subroutine, an address associated with the second OS executable via a data structure stored by the volatile memory medium; retrieve, by the first OS executable, the address of the volatile memory medium associated with the second OS executable from the data structure; and copy, by the first OS executable, the second OS executable from the volatile memory medium to the second non-volatile memory medium based at least on the second address of the volatile memory medium associated with the second OS executable.

In one or more embodiments, the data structure may include a table that is compliant with an Advanced Configuration and Power Interface (ACPI) table. In one or more embodiments, the system information associated with the IHS may include at least one of a service tag associated with the IHS and an identifier associated with the IHS. In one or more embodiments, the power configuration information associated with the IHS may indicate at least one of that the IHS is in a battery mode, that the IHS is optimized to utilize a battery, that the IHS is optimized for a high performance mode, and that the IHS is plugged into a power supply. In one or more embodiments, the configuration information may indicate at least on of whether or not an internal camera is enabled, and at least one setting of the IHSFW. In one or more embodiments, the hardware information associated with the IHS may include at least one of an operating speed of the at least one processor, a number of processing cores of the at least one processor, an operating speed of a graphics processing unit, a number of vectors that the graphics processing unit can simultaneously utilize, an amount of random access memory that the IHS includes, and an amount of storage of the second non-volatile memory medium available.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure and its features/advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, which are not drawn to scale, and in which:

FIG. 1A illustrates an example of an information handling system, according to one or more embodiments;

FIG. 1B illustrates another example of an information handling system, according to one or more embodiments;

FIG. 1C illustrates examples of data structures that stores identifiers respectively associated with executables, according to one or more embodiments;

FIG. 1D illustrates examples of portions of a memory medium, according to one or more embodiments;

FIGS. 2A and 2B illustrate an example of a method of operating an information handling system, according to one or more embodiments;

FIG. 3A illustrates an example of providing a first operating system executable to a volatile memory medium, according to one or more embodiments;

FIG. 3B illustrates an example of providing a second operating system executable to a volatile memory medium, according to one or more embodiments;

FIG. 3C illustrates an example of providing a third operating system executable to a volatile memory medium, according to one or more embodiments;

FIG. 3D illustrates an example of providing a first operating system executable to a non-volatile memory medium, according to one or more embodiments;

FIG. 3E illustrates an example of providing a second operating system executable to a non-volatile memory medium, according to one or more embodiments;

FIG. 3F illustrates an example of providing a third operating system executable to a non-volatile memory medium, according to one or more embodiments;

FIGS. 4A and 4B illustrate a second example of a method of operating an information handling system, according to one or more embodiments;

FIG. 5 illustrates an example of utilizing a persistent application that advises how to configure an information handling system, according to one or more embodiments;

FIG. 6 illustrates a third example of a method of operating an information handling system, according to one or more embodiments; and

FIGS. 7A and 7B illustrate another example of a method of operating an information handling system, according to one or more embodiments.

DETAILED DESCRIPTION

In the following description, details are set forth by way of example to facilitate discussion of the disclosed subject matter. It should be apparent to a person of ordinary skill in the field, however, that the disclosed embodiments are examples and not exhaustive of all possible embodiments.

As used herein, a reference numeral refers to a class or type of entity, and any letter following such reference numeral refers to a specific instance of a particular entity of that class or type. Thus, for example, a hypothetical entity referenced by ‘12A’ may refer to a particular instance of a particular class/type, and the reference ‘12’ may refer to a collection of instances belonging to that particular class/type or any one instance of that class/type in general.

In one or more embodiments, an operating system (OS) may provide a capability, in a new installation or in a reinstallation, which works in conjunction with information handling system firmware (IHSFW) to execute an IHSFW-based platform application. For example, the platform application may enable an information handling system (IHS) manufacturer with an option to install an application on an IHS where existing applications of the OS may not be adequate. In one instance, the platform application may be configured to accommodate specific characteristics of an IHS, such as specific characteristic of a hardware component of the IHS. In another instance, the platform application may be configured to configure one or more portions of an IHS, which may be specific to the IHS, such as specific one or more power utilization configurations of the IHS. In one or more embodiments, the platform application may be installed after the OS is installed or after the OS is reinstalled. In one example, in this fashion, the platform application may have continuity and/or persistence across multiple OS installations on same or different non-volatile memory media (e.g., solid state drive(s), hard drive(s), etc.). In a second example, in this fashion, the platform application may endure across multiple OS installations on same or different non-volatile memory media (e.g., solid state drive(s), hard drive(s), etc.). In another example, in this fashion, the platform application may be installed or reinstalled across multiple OS installations on same or different non-volatile memory media (e.g., solid state drive(s), hard drive(s), etc.).

In one or more embodiments, multiple platform applications may be installed via a platform application controller. For example, the OS may instruct a processor of the IHS to execute the platform application controller. For instance, the platform application controller may include one or more structures and/or one or more functionalities of a session manager. In one or more embodiments, the session manager may instruct the processor to execute multiple additional platform applications.

In one or more embodiments, a first data structure may be populated with information associated with a platform application. For example, the first data structure may include a first table. In one instance, the first table may be compliant with an Advanced Configuration and Power Interface (ACPI) table. In another instance, the first table may be or include an ACPI table. In one or more embodiments, the first data structure may be utilized to communicate information, associated with the platform application, between the IHSFW and the OS.

In one or more embodiments, a second data structure may be populated with information associated with one or more additional platform applications. For example, the second data structure may include a second table. In one instance, the second table may be compliant with an ACPI table. In another instance, the second table may be or include an ACPI table. In one or more embodiments, the second data structure may be utilized to communicate information, associated with the one or more additional platform applications, between the OS and the IHSFW.

In one or more embodiments, the one or more additional platform applications may enable one or more options to install the one or more additional applications on the IHS where existing applications of the OS may not be adequate. For example, the one or more additional platform applications may provide one or more advantages over a single platform application. In one instance, utilizing the one or more additional platform applications may provide a granular control over enabling and/or disabling the one or more additional applications. In a second instance, utilizing the one or more additional platform applications may provide one or more options for one or more third-party vendors to provide their respective one or more platform applications without having to incorporate such functionalities into a single platform application. In another instance, utilizing the one or more additional platform applications may provide one or more options for an original equipment manufacturer (OEM) (e.g., Dell, Lenovo, Apple, HP, etc.) to provide its respective one or more platform applications without having to incorporate such functionalities into a single platform application. As an example, the OEM may provide a platform application, which may be utilized to configure an information handling system that the OEM manufactures. For instance, the OEM may provide a platform application, which may be utilized to configure one or more power settings of an information handling system that the OEM manufactures.

In one or more embodiments, during a launch of the OS, a session manager may load the platform controller and instruct the processor to execute the platform controller. In one or more embodiments, the platform controller may perform a process that loaded and executed the platform controller to load and instruct the processor to execute the one or more additional platform applications. For example, the platform controller may access the second data structure and retrieve information associated with the one or more additional platform applications. In one or more embodiments, the one or more additional platform applications may be stored via a non-volatile memory medium of the IHS. For example, the non-volatile memory medium of the IHS may include a hard disk drive, a solid state drive, etc. In one instance, the one or more additional platform applications may be stored via a non-volatile memory medium of the IHS where the OS is stored. In another instance, the one or more additional platform applications may be stored via a non-volatile memory medium of the IHS where executables that are executed via an OS context are stored.

In one or more embodiments, an OS may provide a capability in a baseline OS (e.g., a clean install), which may work in conjunction with information handling system firmware to execute a single information handling system firmware based platform binary application. For example, a platform binary application may enable an information handling system vendor to manage and/or configure a small set of software where existing OS tools are not enough for installing software that is specific for the execution of the OS on an information handling system produced by the information handling system vendor. In one or more embodiments, a platform binary application may be utilized to provide features such as anti-theft services and/or persistence of OS-based provisioning applications.

In one or more embodiments, OS power performance has an important component of overall user satisfaction of an information handling system. With an introduction of modern standby, an information handling system may be configured to provide “instant on” behavior while maintaining a significantly low power state (e.g., near legacy S3 performance). As an example, modern standby may rely upon hardware components of an information handling system and software to work in concert to permit services and the hardware components to idle into an optimal behavior. After an installation of an OS, an IHS may perform well, or at least as expected by a user. When additional applications and/or third party hardware is introduced to the IHS, the IHS may never idle, may run at full power, may wake up to poll for a status of a hardware component, and/or may wake up to check for an email update, among others, and may not be able to enter back into a low power state.

In one or more embodiments, power management configuration settings associated with a user may be susceptible to small changes that may introduce dramatic behavior and/or reconfigure an IHS in a non-optimal manner. In one or more embodiments, an OS may support in depth reporting of services and/or applications that are causing poor behavior and/or dramatic behavior but may lack a policy implementation that may be utilized to make proper utilization of an IHS. As an example, a first user may receive a first IHS from an IHS vender and may install applications on the first IHS. Over time, power consumption during modern standby may become greater and greater and may eventually become non-functional. As a second example, a second user may receive a second IHS from the IHS vender. The IHS vender may identify configuration changes, which have been tested to provide improved one or more power management configurations. As a third example, a third user may receive a third IHS from the information handling system vender, and the third user may update an OS installed on the third IHS. One or more configurations associated with the third information handling system may be or may not be changed to new default one or more configurations associated with the updated OS. In one or more embodiments, a persistent application, such as a platform application, may be utilized to mitigate or eliminate power configuration issues, which may have resulted from updates and/or changes associated with an IHS.

Turning now to FIG. 1A, an example of an information handling system is illustrated, according to one or more embodiments. An IHS 110 may include a hardware resource or an aggregate of hardware resources operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, and/or utilize various forms of information, intelligence, or data for business, scientific, control, entertainment, or other purposes, according to one or more embodiments. For example, IHS 110 may be a personal computer, a desktop computer system, a laptop computer system, a server computer system, a mobile device, a tablet computing device, a personal digital assistant (PDA), a consumer electronic device, an electronic music player, an electronic camera, an electronic video player, a wireless access point, a network storage device, or another suitable device and may vary in size, shape, performance, functionality, and price. In one or more embodiments, a portable IHS 110 may include or have a form factor of that of or similar to one or more of a laptop, a notebook, a telephone, a tablet, and a PDA, among others. For example, a portable IHS 110 may be readily carried and/or transported by a user (e.g., a person). In one or more embodiments, components of IHS 110 may include one or more storage devices, one or more communications ports for communicating with external devices as well as various input and output (I/O) devices, such as a keyboard, a mouse, and a video display, among others. In one or more embodiments, IHS 110 may include one or more buses operable to transmit communication between or among two or more hardware components. In one example, a bus of IHS 110 may include one or more of a memory bus, a peripheral bus, and a local bus, among others. In another example, a bus of IHS 110 may include one or more of a Micro Channel Architecture (MCA) bus, an Industry Standard Architecture (ISA) bus, an Enhanced ISA (EISA) bus, a Peripheral Component Interconnect (PCI) bus, HyperTransport (HT) bus, an inter-integrated circuit (I²C) bus, a serial peripheral interface (SPI) bus, a low pin count (LPC) bus, an enhanced serial peripheral interface (eSPI) bus, a universal serial bus (USB), a system management bus (SMBus), and a Video Electronics Standards Association (VESA) local bus, among others.

In one or more embodiments, IHS 110 may include firmware that controls and/or communicates with one or more hard drives, network circuitry, one or more memory devices, one or more I/O devices, and/or one or more other peripheral devices. For example, firmware may include software embedded in an IHS component utilized to perform tasks. In one or more embodiments, firmware may be stored in non-volatile memory, such as storage that does not lose stored data upon loss of power. In one example, firmware associated with an IHS component may be stored in non-volatile memory that is accessible to one or more IHS components. In another example, firmware associated with an IHS component may be stored in non-volatile memory that may be dedicated to and includes part of that component. For instance, an embedded controller may include firmware that may be stored via non-volatile memory that may be dedicated to and includes part of the embedded controller.

As shown, IHS 110 may include a processor 120, a volatile memory medium 150, non-volatile memory media 160 and 170, an I/O subsystem 180, and a network interface 182. As illustrated, volatile memory medium 150, non-volatile memory media 160 and 170, I/O subsystem 180, and network interface 182 may be communicatively coupled to processor 120.

In one or more embodiments, one or more of volatile memory medium 150, non-volatile memory media 160 and 170, I/O subsystem 180, and network interface 182 may be communicatively coupled to processor 120 via one or more buses, one or more switches, and/or one or more root complexes, among others. In one example, one or more of volatile memory medium 150, non-volatile memory media 160 and 170, I/O subsystem 180, and network interface 182 may be communicatively coupled to processor 120 via one or more PCI-Express (PCIe) root complexes. In another example, one or more of an I/O subsystem 180 and a network interface 182 may be communicatively coupled to processor 120 via one or more PCIe switches.

In one or more embodiments, the term “memory medium” may mean a “storage device”, a “memory”, a “memory device”, a “tangible computer readable storage medium”, and/or a “computer-readable medium”. For example, computer-readable media may include, without limitation, storage media such as a direct access storage device (e.g., a hard disk drive, a floppy disk, etc.), a sequential access storage device (e.g., a tape disk drive), a compact disk (CD), a CD-ROM, a digital versatile disc (DVD), a random access memory (RAM), a read-only memory (ROM), a one-time programmable (OTP) memory, an electrically erasable programmable read-only memory (EEPROM), and/or a flash memory, a solid state drive (SSD), or any combination of the foregoing, among others.

In one or more embodiments, one or more protocols may be utilized in transferring data to and/or from a memory medium. For example, the one or more protocols may include one or more of small computer system interface (SCSI), Serial Attached SCSI (SAS) or another transport that operates with the SCSI protocol, advanced technology attachment (ATA), serial ATA (SATA), a USB interface, an Institute of Electrical and Electronics Engineers (IEEE) 1394 interface, a Thunderbolt interface, an advanced technology attachment packet interface (ATAPI), serial storage architecture (SSA), integrated drive electronics (IDE), or any combination thereof, among others.

Volatile memory medium 150 may include volatile storage such as, for example, RAM, DRAM (dynamic RAM), EDO RAM (extended data out RAM), SRAM (static RAM), etc. One or more of non-volatile memory media 160 and 170 may include nonvolatile storage such as, for example, a read only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM, NVRAM (non-volatile RAM), ferroelectric RAM (FRAM), a magnetic medium (e.g., a hard drive, a floppy disk, a magnetic tape, etc.), optical storage (e.g., a CD, a DVD, a BLU-RAY disc, etc.), flash memory, a SSD, etc. In one or more embodiments, a memory medium can include one or more volatile storages and/or one or more nonvolatile storages.

In one or more embodiments, network interface 182 may be utilized in communicating with one or more networks and/or one or more other information handling systems. In one example, network interface 182 may enable IHS 110 to communicate via a network utilizing a suitable transmission protocol and/or standard. In a second example, network interface 182 may be coupled to a wired network. In a third example, network interface 182 may be coupled to an optical network. In another example, network interface 182 may be coupled to a wireless network.

In one or more embodiments, network interface 182 may be communicatively coupled via a network to a network storage resource. For example, the network may be implemented as, or may be a part of, a storage area network (SAN), personal area network (PAN), local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a wireless local area network (WLAN), a virtual private network (VPN), an intranet, an Internet or another appropriate architecture or system that facilitates the communication of signals, data and/or messages (generally referred to as data). For instance, the network may transmit data utilizing a desired storage and/or communication protocol, including one or more of Fibre Channel, Frame Relay, Asynchronous Transfer Mode (ATM), Internet protocol (IP), other packet-based protocol, Internet SCSI (iSCSI), or any combination thereof, among others.

In one or more embodiments, processor 120 may execute processor instructions in implementing one or more systems, one or more flowcharts, one or more methods, and/or one or more processes described herein. In one example, processor 120 may execute processor instructions from one or more of memory media 150, 160, and 170 in implementing one or more systems, one or more flowcharts, one or more methods, and/or one or more processes described herein. In another example, processor 120 may execute processor instructions via network interface 182 in implementing one or more systems, one or more flowcharts, one or more methods, and/or one or more processes described herein.

In one or more embodiments, processor 120 may include one or more of a system, a device, and an apparatus operable to interpret and/or execute program instructions and/or process data, among others, and may include one or more of a microprocessor, a microcontroller, a digital signal processor (DSP), an application specific integrated circuit (ASIC), and another digital or analog circuitry configured to interpret and/or execute program instructions and/or process data, among others. In one example, processor 120 may interpret and/or execute program instructions and/or process data stored locally (e.g., via memory media 150, 160, and 170 and/or another component of IHS 110). In another example, processor 120 may interpret and/or execute program instructions and/or process data stored remotely (e.g., via a network storage resource).

In one or more embodiments, I/O subsystem 180 may represent a variety of communication interfaces, graphics interfaces, video interfaces, user input interfaces, and/or peripheral interfaces, among others. For example, I/O subsystem 180 may include one or more of a touch panel and a display adapter, among others. For instance, a touch panel may include circuitry that enables touch functionality in conjunction with a display that is driven by a display adapter.

As shown, non-volatile memory medium 160 may include an OS 162, and applications (APPs) 167-169. In one or more embodiments, one or more of OS 162 and APPs 167-169 may include processor instructions executable by processor 120. In one example, processor 120 may execute processor instructions of one or more of OS 162 and APPs 167-169 via non-volatile memory medium 160. In another example, one or more portions of the processor instructions of the one or more of OS 162 and APPs 167-169 may be transferred to volatile memory medium 150, and processor 120 may execute the one or more portions of the processor instructions of the one or more of OS 162 and APPs 167-169 via volatile memory medium 150.

In one or more embodiments, OS 162 may be or include an UNIX® operating system. In one or more embodiments, OS 162 may be or include an Unix-like operating system. For instance, the Unix-like operating system may be or include LINUX®, FREEBSD®, NETBSD®, MACOS®, OpenBSD, Minix, Xinu, or Darwin, among others. In another example, OS 162 may be or include a portable operating system interface (POSIX) compliant operating system. In one or more embodiments, OS 162 may be or include a MICROSOFT® WINDOWS® operating system.

As illustrated, non-volatile memory medium 170 may include IHSFW 172. In one or more embodiments, IHSFW 172 may include processor instructions executable by processor 120. For example, IHSFW 172 may include one or more structures and/or one or more functionalities of and/or compliant with one or more of a basic input/output system (BIOS), an Extensible Firmware Interface (EFI), a Unified Extensible Firmware Interface (UEFI), and an ACPI, among others. In one instance, processor 120 may execute processor instructions of IHSFW 172 via non-volatile memory medium 170. In another instance, one or more portions of the processor instructions of IHSFW 172 may be transferred to volatile memory medium 150, and processor 120 may execute the one or more portions of the processor instructions of IHSFW 172 via volatile memory medium 150. As shown, non-volatile memory medium 170 may include IHS initialization executables 173A-173N. In one or more embodiments, IHS initialization executables 173A-173N may be executable in an environment of IHSFW 172. For example, IHS initialization executables 173A-173N may be executable in a Driver Execution Environment (DXE) of IHSFW 172.

In one or more embodiments, an IHS initialization executable 173 may be an initializing executable. For example, an IHS initialization executable 173 may at least a portion of IHS 110. For instance, IHSFW 172 may discover and execute an IHS initialization executable 173 to initialize at least a portion of IHS 110. In one or more embodiments, an IHS initialization executable 173 may be associated with a portable execution/common object file format (PE/COFF). For example, IHSFW 172 may include a PE/COFF loader to load and execute an IHS initialization executable 173. In one or more embodiments, an IHS initialization executable 173 may be a DXE driver. For example, IHSFW 172 may include a DXE dispatcher that may discover and execute an IHS initialization executable 173 to initialize at least a portion of IHS 110.

As illustrated, non-volatile memory medium 170 may include OS executables 174A-174N. In one or more embodiments, OS executables 174A-174N may be executable in an environment of OS 162. For example, one or more of OS executables 174A-174N may be platform applications.

In one or more embodiments, OS 162 may include a management information exchange. In one example, the management information exchange may permit multiple components to exchange management information associated with managed elements and/or may permit control and/or management of the managed elements. In another example, the management information exchange may include a driver and/or a driver model that may provide an OS interface through which managed elements (e.g., elements of IHS 110) may provide information and/or notifications, among others. In one instance, the management information exchange may be or include a Windows Management Interface (WMI) for ACPI (available from Microsoft Corporation). In another instance, the management information exchange may be or include a Common Information Model (CIM) (available via the Distributed Management Task Force). In one or more embodiments, the management information exchange may include a combination of the WMI and the CIM. For example, WMI may be and/or may be utilized as an interface to the CIM. For instance, the WMI may be utilized to provide and/or send CIM object information to OS 162.

In one or more embodiments, processor 120 and one or more components of IHS 110 may be included in a system-on-chip (SoC). For example, the SoC may include processor 120 and a platform controller hub (not specifically illustrated). In one or more embodiments, IHS 110 may include a battery 130. For example, battery 130 may store energy. For instance, battery 130 may provide power to one or more components of IHS 110. As an example, the one or more components of IHS 110 may include one or more of processor 120, volatile memory medium 150, non-volatile memory medium 160, non-volatile memory medium 170, PO subsystem 180, and network interface 182, among others. In one or more embodiments, battery 130 may provide power to one or more peripherals coupled to IHS 110. For example, the one or more peripherals coupled to IHS 110 may include one or more of a pointing device (e.g., a mouse, a trackpad, a trackball, etc.), a keyboard, and a mobile communications device, among others. For instance, battery 130 may provide power to the one or more peripherals coupled to IHS 110 via a USB interface.

Turning now to FIG. 1B, another example of an information handling system is illustrated, according to one or more embodiments. In one or more embodiments, IHS initialization executable 173A may be executed. For example, IHS initialization executable 173A may be executed via at least a portion of IHSFW 172. For instance, the at least the portion of IHSFW 172 may determine that non-volatile memory medium 170 includes IHS initialization executable 173A and may instruct processor 120 to execute IHS initialization executable 173A. In one or more embodiments, IHSFW 172 may include and/or may provide an environment. For example, IHSFW 172 may include and/or may provide a DXE. In one or more embodiments, an executable 173 may be a DXE driver. For example, the DXE driver may be executed in a DXE. For instance, processor 120 may execute the DXE driver via the DXE and/or may execute the DXE driver within the DXE. In one or more embodiments, a DXE driver may typically be associated with a hardware component of IHS 110. For example, the DXE driver may enable IHSFW 172 to communicate with the hardware component. In one or more embodiments, a DXE driver may not be associated with a hardware component of IHS 110. For example, an IHS initialization executable 173 may be a DXE driver but may not be associated with a hardware component of IHS 110. For instance, an executable 173 may permit instructions of processor 120 to execute via the DXE.

As shown, IHS initialization executable 173A may include a subroutine 175. In one or more embodiments, subroutine 175 may include instructions, executable by processor 120, to implement at least a portion of one or more systems, at least a portion of one or more flowcharts, at least a portion of one or more methods, and/or at least a portion of one or more processes described herein. For example, processor 120 may execute processor instructions of subroutine 175 in implementing at least a portion of one or more systems, at least a portion of one or more flowcharts, at least a portion of one or more methods, and/or at least a portion of one or more processes described herein.

In one or more embodiments, subroutine 175 may be registered with at least a portion of IHSFW 172. For example, executing IHS initialization executable 173A may register subroutine 175 with at least a portion of IHSFW 172. In one or more embodiments, one or more of IHS initialization 173B-173N may call subroutine 175. For example, the one or more of IHS initialization executables 173B-173N may call subroutine 175 after subroutine 175 is registered. For instance, the one or more of executables 173B-173N may instruct processor 120 to execute subroutine 175.

In one or more embodiments, a data structure 176A may be created in volatile memory medium 150. For example, executing IHS initialization executable 173A may create data structure 176A in volatile memory medium 150. In one or more embodiments, data structure 176A may be compliant with an ACPI table. In one or more embodiments, data structure 176A may include an ACPI table.

In one or more embodiments, OS executable 174A may be copied from non-volatile memory medium 170 to volatile memory medium 150. For example, IHS initialization executable 173A may copy OS executable 174A from non-volatile memory medium 170 to volatile memory medium 150. In one instance, copying OS executable 174A from non-volatile memory medium 170 to volatile memory medium 150 may include retrieving OS executable 174A from non-volatile memory medium 170. In another instance, copying OS executable 174A from non-volatile memory medium 170 to volatile memory medium 150 may include writing executable 174A to volatile memory medium 150.

In one or more embodiments, an identifier may be associated with OS executable 174A. For example, the identifier associated with OS executable 174A may include a globally unique identifier (GUID). In one or more embodiments, the GUID may include a number. For example, the GUID may include a 128-bit number. In one or more embodiments, when generated via one or more methods, globally unique identifiers (GUIDs) may be unique for practical purposes. For example, the uniqueness of GUIDs may not depend on a central registration authority or coordination between parties generating the GUIDs. Although a probability that a GUID will be duplicated may not be zero, the probability that a GUID will be duplicated is close enough to zero to be negligible, according to one or more embodiments. In one or more embodiments, a GUID may be or include a universally unique identifier (UUID).

In one or more embodiments, data structure 176A may store the identifier associated with OS executable 174A. For example, as illustrated in FIG. 1C, data structure 176A may store an identifier 177A associated with OS executable 174A. In one or more embodiments, data structure 176A may store an address of volatile memory medium 150 associated with OS executable 174A. For example, as illustrated in FIG. 1C, data structure 176A may store an address 178A associated with OS executable 174A. In one instance, address 178A of volatile memory medium 150 associated with executable 174A may be a real address of volatile memory medium 150. In another instance, address 178A of volatile memory medium 150 associated with OS executable 174A may be a virtual address associated with a real address of volatile memory medium 150. In one or more embodiments, the identifier associated with OS executable 174A may be utilized to access address 178A of volatile memory medium 150 associated with OS executable 174A. For example, data structure 176A may match identifier 177A associated with OS executable 174A with address 178A of volatile memory medium 150 associated with OS executable 174A.

Referring back to FIG. 1B, in one or more embodiments, IHS initialization executable 173B may be executed. For example, IHS initialization executable 173B may be executed via at least a portion of IHSFW 172. For instance, the at least the portion of IHSFW 172 may determine that non-volatile memory medium 170 includes IHS initialization executable 173B and may instruct processor 120 to execute IHS initialization executable 173B.

In one or more embodiments, IHS initialization executable 173B may call subroutine 175. For example, IHS initialization executable 173B may instruct processor 120 to execute subroutine 175. In one or more embodiments, a data structure 176B may be created in volatile memory medium 150. For example, subroutine 175 may create data structure 176B in volatile memory medium 150. In one instance, subroutine 175 may create data structure 176B in volatile memory medium 150 in response to being called by IHS initialization executable 173B. In another instance, subroutine 175 may create data structure 176B in volatile memory medium 150 in response to determining that data structure 176B does not exist in volatile memory medium 150. In one or more embodiments, data structure 176B may be compliant with an ACPI table. In one or more embodiments, data structure 176B may include an ACPI table.

In one or more embodiments, OS executable 174B may be copied from non-volatile memory medium 170 to volatile memory medium 150. For example, IHS initialization executable 173B may copy OS executable 174A from non-volatile memory medium 170 to volatile memory medium 150. In one instance, copying OS executable 174B from non-volatile memory medium 170 to volatile memory medium 150 may include retrieving OS executable 174B from non-volatile memory medium 170. In another instance, copying OS executable 174B from non-volatile memory medium 170 to volatile memory medium 150 may include writing OS executable 174B to volatile memory medium 150. In one or more embodiments, an identifier may be associated with OS executable 174B. For example, the identifier associated with executable 174B may include a GUID.

In one or more embodiments, data structure 176B may store the identifier associated with OS executable 174B. For example, as illustrated in FIG. 1C, data structure 176B may store an identifier 177B associated with OS executable 174B. In one or more embodiments, data structure 176B may store an address of volatile memory medium 150 associated with OS executable 174B. For example, as illustrated in FIG. 1C, data structure 176B may store an address 178B of volatile memory medium 150 associated with OS executable 174B. In one instance, address 178B of volatile memory medium 150 associated with OS executable 174B may be a real address of volatile memory medium 150. In another instance, address 178B of volatile memory medium 150 associated with OS executable 174B may be a virtual address associated with a real address of volatile memory medium 150. In one or more embodiments, an address 178 may indicate to processor 120 where to start executing an OS executable 174. In one or more embodiments, identifier 177B associated with OS executable 174B may be utilized to access the address of volatile memory medium 150 associated with OS executable 174B. For example, data structure 176B may match identifier 177B associated with OS executable 174B with address 178B of volatile memory medium 150 associated with OS executable 174B.

In one or more embodiments, one or more methods and/or one or more processes described above with reference to executable 174B may be utilized with OS executables 174C-174N. For example, OS executables 174C-174N may be copied from non-volatile memory medium 170 to volatile memory medium 150. For instance, one or more of IHS initialization executables 173C-173N may be executed and may respectively copy one or more of OS executables 174C-174N from non-volatile memory medium 170 to volatile memory medium 150. In one or more embodiments, data structure 176B may store identifiers 177C-177N respectively associated with executables 174C-174N. In one or more embodiments, data structure 176B may store addresses 178C-178N of volatile memory medium 150 respectively associated with OS executables 174C-174N. For example, data structure 176B may match identifiers 177C-177N respectively associated with OS executables 174C-174N with respective addresses 178C-178N of volatile memory medium 150 associated with OS executables 174C-174N. For instance, a data structure 176 may include a table. In one or more embodiments, a table entry of a data structure 176 may store an identifier 177 and an address 178.

Referring back to FIG. 1B, in one or more embodiments, OS executable 174A may be copied from volatile memory medium 150 to non-volatile memory medium 160. For example, OS 162 may copy OS executable 174A from volatile memory medium 150 to non-volatile memory medium 160. In one instance, copying OS executable 174A from volatile memory medium 150 to non-volatile memory medium 160 may include retrieving executable 174A from volatile memory medium 150. In another instance, copying OS executable 174A from volatile memory medium 150 to non-volatile memory medium 160 may include writing executable 174A to non-volatile memory medium 160. In one or more embodiments, OS 162 may include a MICROSOFT® WINDOWS® operating system. For example, a MICROSOFT® WINDOWS® operating system session manager may copy OS executable 174A from volatile memory medium 150 to non-volatile memory medium 160. For instance, the MICROSOFT® WINDOWS® operating system session manager may be executed via a startup process of the MICROSOFT® WINDOWS® operating system. In one or more embodiments, OS 162 may launch executable 174A. For example, launching OS executable 174A may include instructing processor 120 to execute executable 174A. For instance, the MICROSOFT® WINDOWS® operating system session manager may instruct processor 120 to execute OS executable 174A. In one or more embodiments, executable 174A may be a platform controller.

In one or more embodiments, OS executable 174A may determine that data structure 176B exists in volatile memory medium 150. For example, OS executable 174A may access data structure 176B. For instance, OS executable 174A may access identifiers stored via data structure 176B. In one or more embodiments, OS executable 174A may utilize an identifier associated with executable 174B. For example, OS executable 174A may determine an address of volatile memory medium associated with OS executable 174B based at least on the identifier associated with OS executable 174B.

In one or more embodiments, OS executable 174A may copy OS executable 174B from volatile memory medium 150 to non-volatile memory medium 160. In one example, copying OS executable 174B from volatile memory medium 150 to non-volatile memory medium 160 may include retrieving OS executable 174B from volatile memory medium 150. In another example, copying OS executable 174B from volatile memory medium 150 to non-volatile memory medium 160 may include writing OS executable 174B to non-volatile memory medium 160.

In one or more embodiments, one or more methods and/or one or more processes described above with reference to executable 174B may be utilized with executables 174C-174N. For example, OS executables 174C-174N may be copied from volatile memory medium 150 to volatile non-memory medium 160. For instance, OS executable 174A may copy one or more of OS executables 174C-174N from volatile memory medium 150 to volatile non-memory medium 160. In one or more embodiments, data structure 176B may store identifiers respectively associated with OS executables 174C-174N. In one or more embodiments, data structure 176B may store addresses of volatile memory medium 150 respectively associated with OS executables 174C-174N. For example, data structure 176B may match the identifiers respectively associated with OS executables 174C-174N with respective addresses of volatile memory medium 150 associated with OS executables 174C-174N. In one or more embodiments, OS executable 174A may determine an address of addresses 178B-178N via a respective identifier of identifiers 177B-177N. For example, OS executable 174A may copy an executable of OS executables 174B-174N from volatile memory medium 150 to volatile non-memory medium 160 based at least on the determined address.

In one or more embodiments, information of data structure 176B may be provided to OS executable 174A via a command line. For example, identifiers 177B-177N and respectively associated addresses 178B-178N may be passed on the command line to OS executable 174A. In one instance, a script may pass identifiers 177B-177N and respectively associated addresses 178B-178N on the command line to OS executable 174A. In another instance, an executable may pass identifiers 177B-177N and respectively associated addresses 178B-178N on the command line to OS executable 174A. In one or more embodiments, data structure 176B may not be created or may not be utilized. For example, identifiers 177B-177N and respectively associated addresses 178B-178N may be passed via an instruction to run OS executable 174A without creating data structure 176B. For instance, identifiers 177B-177N and respectively associated addresses 178B-178N may be passed on a command line to OS executable 174A without creating data structure 176B.

In one or more embodiments, volatile memory medium 150 may be associated with multiple portions. Referring to FIG. 1D, for example, volatile memory medium 150 may be associated with multiple memory portions 152A-152C. For instance, a memory portion 152 may be associated with an address range. As an example, memory portions 152A-152C may be respectively associated with different address ranges. Although three memory portions are illustrated in FIG. 1D, any number of memory portions may be utilized, according to one or more embodiments. In one or more embodiments, memory portion 152A may be associated with an address range that is accessible by IHSFW 172 and/or OS 162. For example, memory portion 152A may be associated with an address range that is accessible by a kernel of OS 162. In one instance, the address range associated with memory portion 152A may be accessed in a privileged mode. In another instance, the address range associated with memory portion 152A may not be accessible by a user space application and/or may not be accessible by instructions that are executed via user space.

In one or more embodiments, OS executable 174A may include a driver 179. For example, driver 179 may access memory portion 152A. In one instance, driver 179 may access a kernel of OS 162, which may access memory portion 152A. In another instance, driver 179 may include a loadable kernel module for a kernel of OS 162, which may access memory portion 152A. As an example, memory portion 152A may be accessible by a kernel of OS 162 or a loadable kernel module for the kernel of OS 162. For instance, memory portion 152A may be associated with kernel space, and memory portion 152B may be associated with user space. Driver 179 may enable OS executable 174A to access memory portion 152A (e.g., kernel space). For example, driver 179 may be executed in a privileged mode, which may access memory portion 152A.

In one or more embodiments, OS 162 may instruct processor 120 to execute one or more of executables 174B-174N. In one example, after OS 162 finishes a startup portion of OS 162, OS 162 may instruct processor 120 to execute one or more of OS executables 174B-174N. In another example, after OS 162 finishes the startup portion of OS 162, OS 162 may not instruct processor 120 to execute other one or more of OS executables 174B-174N. For instance, a user, a service, or an application (e.g., an application of APPs 167-169) may launch (e.g., start) the other one or more of OS executables 174B-174N. As an example, the other one or more of OS executables 174B-174N may include one or more applications. For instance, an executable of the other one or more of OS executables 174B-174N may include an application that includes one or more structures and/or one or more functionalities of an application of APPs 167-169.

In one or more embodiments, utilizing one or more systems, one or more methods, and/or one or more processes described herein, one or more of OS executables 174B-174N may have continuity across formatting non-volatile memory medium 160 and/or across installations of one or more operating systems on non-volatile memory medium 160. For example, one or more of OS executables 174B-174N may endure across formatting non-volatile memory medium 160. For instance, one or more of OS executables 174B-174N may be reinstalled after formatting non-volatile memory medium 160. In one or more embodiments, utilizing one or more systems, one or more methods, and/or one or more processes described herein, one or more of OS executables 174B-174N may have continuity across another installation of an operating system. For example, one or more of OS executables 174B-174N may endure across another installation of an operating system. For instance, one or more of executables 174B-174N may be reinstalled after another installation of an operating system.

Turning now to FIGS. 2A and 2B, an example of a method of operating an information handling system is illustrated, according to one or more embodiments. At 210, at least a portion of IHSFW from a first non-volatile memory medium of the information handling system may be executed by a processor of the information handling system. For example, at least a portion of IHSFW 172, from non-volatile memory medium 170 of IHS 110, may be executed by processor 120 of IHS 110. In one or more embodiments, before executing, by the processor, the at least the portion of IHSFW, an operating system may be installed on a second non-volatile memory medium of the information handling system, different from the first non-volatile memory medium. For example, before executing, by processor 120, the at least the portion of IHSFW 172, OS 162 may be installed on non-volatile memory medium 160. In one or more embodiments, the first non-volatile memory medium may include a serial interface flash memory device. For instance, the serial interface flash memory device may be compliant with a serial bus and/or a serial protocol of a serial interface described herein.

At 215, a first executable that is configured to be executed by the processor may be retrieved from the first non-volatile memory medium. For example, IHS initialization executable 173A may be retrieved from non-volatile memory medium 170. At 220, the first executable may be executed by the processor via an environment associated with the IHSFW. For example, IHS initialization executable 173A may be executed by processor 120 via an environment associated with the IHSFW 172. In one or more embodiments, the environment associated with the IHSFW 172 may include a DXE. For example, a first DXE driver may include the first executable. For instance, a first DXE driver may include IHS initialization executable 173A.

At 225, a subroutine, configured to add one or more identifiers respectively associated with one or more executables to a data structure stored via a volatile memory medium of the information handling system, may be registered. For example, subroutine 175, configured to add one or more identifiers 177B-177N respectively associated with one or more of OS executables 174B-174N to data structure 176B stored via volatile memory medium 150. In one or more embodiments, the subroutine may be registered with the at least the portion of the IHSFW. In one or more embodiments, the data structure stored via the volatile memory medium may include a table that is compliant with an ACPI table. For example, the table may be registered with an ACPI service. In one or more embodiments, the operating system may access the table via the ACPI service. For example, OS 162 may access the table via the ACPI service. In one or more embodiments, OS 162 may access the ACPI service via a management information exchange. For example, OS 162 may access the ACPI service via one or more of a WMI and a CIM, among others.

At 230, a second executable may be copied, by the first executable, from the first non-volatile memory medium to the volatile memory medium. For example, OS executable 174A may be copied, by executable 173A, from non-volatile memory medium 170 to volatile memory medium 150. At 235, a third executable that is configured to be executed by the processor may be retrieved from the first non-volatile memory medium. For example, IHS initialization executable 173B may be retrieved from non-volatile memory medium 170.

At 240, the third executable may be executed by the processor via the environment associated with the IHSFW. For example, IHS initialization executable 173B may be executed by processor 120 via the environment associated with the IHSFW 172. In one or more embodiments, the environment associated with the IHSFW 172 may be a DXE. For example, a second DXE driver may include the third executable. For instance, a second DXE driver may include IHS initialization executable 173B. At 245, a fourth executable may be copied from the first non-volatile memory medium to the volatile memory medium. For example, executable 174B may be copied from non-volatile memory medium 170 to volatile memory medium 150.

At 250, the subroutine may be called by the third executable. For example, IHS initialization executable 173B may call subroutine 175. In one or more embodiments, calling the subroutine may include instructing the processor to execute the subroutine. For example, IHS initialization executable 173B may instruct processor 120 to execute subroutine 175. At 255, the data structure may be configured, by the subroutine, with an identifier associated with the fourth executable. For example, data structure 176B may be configured, by subroutine 175, with an identifier associated with OS executable 174B. For instance, data structure 176B may be configured, by subroutine 175, with identifier 177B associated with executable 174B. In one or more embodiments, the identifier associated with the fourth executable may include a GUID. For example, identifier 177B may include a GUID.

At 260, the identifier associated with the fourth executable may be accessed by the second executable via the data structure. For example, the identifier associated with fourth executable may be access by the second executable via the data structure. At 265, the fourth executable may be retrieved, by the second executable, from the volatile memory medium. For example, OS executable 174B may be retrieved, by OS executable 174A, from volatile memory medium 150.

At 270, the fourth executable may be stored via the second non-volatile memory medium of the information handling system, different from the first non-volatile memory medium. For example, OS executable 174B may be stored via non-volatile memory medium 160. At 275, the fourth executable may be executed by the processor. For example, executable 174B may be executed by processor 120. For instance, OS 162 may instruct processor 120 to execute OS executable 174B.

Turning now to FIG. 3A, an example of providing a first operating system executable to a volatile memory medium is illustrated, according to one or more embodiments. As shown, non-volatile memory medium 170 may store an IHSFW volume (IHSFWV) 310. As illustrated, IHSFWV 310 may include a file 320. In one or more embodiments, at least a portion of IHSFW 172 may determine an ordering of IHS initialization executables 173A-173C based at least on an ordering indicated by file 320. For example, the at least the portion of IHSFW 172 may includes a DXE 330. For instance, file 320 may include an a priori file. In one or more embodiments, a name of file 320 may include a GUID. For example, DXE 330 may store the name of file 320. For instance, DXE 330 may retrieve file 320 from IHSFWV 310 based at least on the name of file 320. In one or more embodiments, DXE 330 may include a DXE dispatcher. For example, the DXE dispatcher may store the name of file 320. For instance, the DXE dispatcher may retrieve file 320 from IHSFWV 310 based at least on the name of file 320.

As shown, DXE 330 may retrieve IHS initialization executable 173A from non-volatile memory medium 170. For example, DXE 330 may retrieve IHS initialization executable 173A from IHSFWV 310. In one or more embodiments, a first IHS initialization executable/OS executable pair may include IHS initialization executable 173A and OS executable (OSE) 174A. In one or more embodiments, processor 120 may execute IHS initialization executable 173A via DXE 330. For example, IHS initialization executable 173A may include a DXE driver. As illustrated, IHS initialization executable 173A may register a subroutine 175 with IHSFW 172. In one or more embodiments, one or more of IHS initialization executables 173B-173N may call subroutine 175.

As shown, OS executable 174A may be retrieved from non-volatile memory medium 170. For example, IHS initialization executable 173A may retrieve OS executable 174A from non-volatile memory medium 170. For instance, OS executable 174A may be retrieved from IHSFWV 310. As illustrated, IHS initialization executable 173A may write OS executable 174A to volatile memory medium 150. For example, IHS initialization executable 173A may write OS executable 174A to volatile memory medium 150 at an address 178A associated with volatile memory medium 150. As shown, IHS initialization executable 173A may create data structure 176A in volatile memory medium 150. In one or more embodiments, data structure 176A may be compliant with an ACPI table. As an example, data structure 176A may include an ACPI table.

As illustrated, IHS initialization executable 173A may write identification (ID) 177A associated with OS executable 174A to data structure 176A. For example, IHS initialization executable 173A may store, via data structure 176A, ID 177A associated with OS executable 174A. As shown, IHS initialization executable 173A may write address 178A associated with OS executable 174A to data structure 176A. For example, IHS initialization executable 173A may store, via data structure 176A, address 178A associated with OS executable 174A. In one or more embodiments, address 178A may be an address of memory portion 152A (of FIG. 1D).

Turning now to FIG. 3B, an example of providing a second operating system executable to a volatile memory medium is illustrated, according to one or more embodiments. As shown, DXE 330 may retrieve IHS initialization executable 173B from non-volatile memory medium 170. For example, DXE 330 may retrieve IHS initialization executable 173B from IHSFWV 310. In one or more embodiments, a second IHS initialization executable/OS executable pair may include IHS initialization executable 173B and OS executable 174B. In one or more embodiments, processor 120 may execute IHS initialization executable 173B via DXE 330. For example, IHS initialization executable 173B may include a DXE driver.

As shown, OS executable 174B may be retrieved from non-volatile memory medium 170. For example, IHS initialization executable 173B may retrieve OS executable 174B from non-volatile memory medium 170. For instance, OS executable 174B may be retrieved from IHSFWV 310. As illustrated, IHS initialization executable 173B may write OS executable 174B to volatile memory medium 150. For example, IHS initialization executable 173B may write OS executable 174B to volatile memory medium 150 at an address 178B associated with volatile memory medium 150. For instance, address 178B may be an address of memory portion 152A.

As shown, IHS initialization executable 173B may call subroutine 175. In one or more embodiments, IHS initialization executable 173B may provide address 178B to subroutine 175. As illustrated, subroutine 175 may create data structure 176B in volatile memory medium 150. In one or more embodiments, data structure 176B may be compliant with an ACPI table. As an example, data structure 176B may include an ACPI table. As illustrated, subroutine 175 may write ID 177B associated with OS executable 174B to data structure 176B. For example, subroutine 175 may store, via data structure 176B, ID 177B associated with OS executable 174B. As shown, subroutine 175 may write address 178B associated with OS executable 174B to data structure 176B. For example, subroutine 175 may store, via data structure 176B, address 178B associated with OS executable 174B.

Turning now to FIG. 3C, an example of providing a third operating system executable to a volatile memory medium is illustrated, according to one or more embodiments. As shown, DXE 330 may retrieve IHS initialization executable 173C from non-volatile memory medium 170. For example, DXE 330 may retrieve IHS initialization executable 173C from IHSFWV 310. In one or more embodiments, a third IHS initialization executable/OS executable pair may include IHS initialization executable 173C and OS executable 174C. In one or more embodiments, processor 120 may execute IHS initialization executable 173C via DXE 330. For example, IHS initialization executable 173C may include a DXE driver.

As shown, OS executable 174C may be retrieved from non-volatile memory medium 170. For example, IHS initialization executable 173C may retrieve OS executable 174C from non-volatile memory medium 170. For instance, OS executable 174C may be retrieved from IHSFWV 310. As illustrated, IHS initialization executable 173C may write OS executable 174C to volatile memory medium 150. For example, IHS initialization executable 173C may write OS executable 174C to volatile memory medium 150 at an address 178C associated with volatile memory medium 150. For instance, address 178C may be an address of memory portion 152A.

As shown, IHS initialization executable 173C may call subroutine 175. In one or more embodiments, IHS initialization executable 173C may provide address 178C to subroutine 175. As illustrated, subroutine 175 may write ID 177C associated with OS executable 174C to data structure 176B. For example, subroutine 175 may store, via data structure 176B, ID 177C associated with OS executable 174C. As shown, subroutine 175 may write address 178C associated with OS executable 174C to data structure 176C. For example, subroutine 175 may store, via data structure 176B, address 178C associated with OS executable 174C.

Turning now to FIG. 3D, an example of providing a first operating system executable to a non-volatile memory medium is illustrated, according to one or more embodiments. As shown, an OS environment 340 may include a startup process 350. In one or more embodiments, OS environment 340 may include OS 162 executed by processor 120. In one or more embodiments, startup process 350 may include a platform application controller. For example, startup process 350 may include one or more structures and/or one or more functionalities of a session manager. In one or more embodiments, the session manager may instruct the processor to execute one or more of OS executables 174A-174N.

As illustrated, startup process 350 may retrieve address 178A from data structure 176A. As shown, startup process 350 may retrieve OS executable 174A from volatile memory medium 150. For example, startup process 350 may retrieve OS executable 174A from volatile memory medium 150 based at least on address 178A. As illustrated, startup process 350 may write OS executable 174A to non-volatile memory medium 160. As shown, non-volatile memory medium 160 may include a file system 360. For example, startup process 350 may write OS executable 174A to file system 360.

In one or more embodiments, IHS initialization executable 173A may not be able to write OS executable 174A to file system 360. For example, IHS initialization executable 173A may not be configured to write OS executable 174A to file system 360. For instance, startup process 350 may copy OS executable 174A from volatile memory medium 150 to file system 360, since IHS initialization executable 173A may not be configured to write OS executable 174A to file system 360.

As illustrated, OS executable 174A may be retrieved from non-volatile memory medium 160. For example, OS executable 174A may be retrieved from file system 360. For example, startup process 350 may retrieve OS executable 174A from file system 360. In one or more embodiments, OS executable 174A may be executed via OS environment 340. For example, processor 120 may execute OS executable 174A via OS environment 340. In one or more embodiments, startup process 350 may instruct processor 120 to execute OS executable 174A. For example, startup process 350 may instruct processor 120 to execute OS executable 174A via OS environment 340.

Turning now to FIG. 3E, an example of providing a second operating system executable to a non-volatile memory medium is illustrated, according to one or more embodiments. As shown, OS executable 174A may retrieve address 178B from data structure 176B. As illustrated, OS executable 174A may retrieve OS executable 174B from volatile memory medium 150. For example, OS executable 174A may retrieve OS executable 174B from volatile memory medium 150 based at least on address 178B. As shown, OS executable 174A may write to OS executable 174B non-volatile memory medium 160. For example, OS executable 174A may write OS executable 174B to file system 360.

In one or more embodiments, IHS initialization executable 173B may not be able to write OS executable 174B to file system 360. For example, IHS initialization executable 173B may not be configured to write OS executable 174B to file system 360. For instance, OS executable 174A may copy OS executable 174B from volatile memory medium 150 to file system 360, since IHS initialization executable 173B may not be configured to write OS executable 174B to file system 360.

As illustrated, OS executable 174B may be retrieved from non-volatile memory medium 160. For example, OS executable 174B may be retrieved from file system 360. For instance, OS executable 174A may retrieve OS executable 174B from file system 360. In one or more embodiments, OS executable 174B may be executed. For example, processor 120 may execute OS executable 174B via OS environment 340. In one instance, OS executable 174A may instruct processor 120 to execute OS executable 174B. In another instance, user input may instruct processor 120 to execute OS executable 174B.

Turning now to FIG. 3F, an example of providing a third operating system executable to a non-volatile memory medium is illustrated, according to one or more embodiments. As shown, OS executable 174A may retrieve address 178C from data structure 176B. As illustrated, OS executable 174A may retrieve OS executable 174C from volatile memory medium 150. For example, OS executable 174A may retrieve OS executable 174C from volatile memory medium 150 based at least on address 178C. As shown, OS executable 174A may write to OS executable 174C non-volatile memory medium 160. For example, OS executable 174A may write OS executable 174C to file system 360.

In one or more embodiments, IHS initialization executable 173C may not be able to write OS executable 174C to file system 360. For example, IHS initialization executable 173C may not be configured to write OS executable 174C to file system 360. For instance, OS executable 174A may copy OS executable 174C from volatile memory medium 150 to file system 360, since IHS initialization executable 173C may not be configured to write OS executable 174C to file system 360.

As illustrated, OS executable 174C may be retrieved from non-volatile memory medium 160. For example, OS executable 174C may be retrieved from file system 360. For instance, OS executable 174A may retrieve OS executable 174C from file system 360. In one or more embodiments, OS executable 174C may be executed. For example, processor 120 may execute OS executable 174C via OS environment 340. In one instance, OS executable 174A may instruct processor 120 to execute OS executable 174C. In another instance, user input may instruct processor 120 to execute OS executable 174C.

Although the examples of FIGS. 3E and 3F illustrate OS executable 174A providing two operating system executables to a non-volatile memory medium, OS executable 174A may provide any number of operating system executables to the non-volatile memory medium, according to one or more embodiments. For example, OS executable 174A may access data structure 176B, where OS executable 174A may obtain addresses 178B-178N (as illustrated in FIG. 1C). For instance, OS executable 174A may provide operating system executables 174B-174N to non-volatile memory medium 160. As an example, OS executable 174A may copy operating system executables 174B-174N from volatile memory medium 150 to non-volatile memory medium 160.

Turning now to FIGS. 4A and 4B, another example of a method of operating an information handling system is illustrated, according to one or more embodiments. At 410, at least one processor of an IHS may execute at least a portion of IHSFW from a first non-volatile memory medium of the IHS. For example, processor 120 may execute at least a portion of IHSFW 172 from non-volatile memory medium 170. At 412, a first IHS initialization executable of a first IHS initialization executable/OS executable pair may be retrieved from the first non-volatile memory medium. For example, IHS initialization executable 173A may be retrieved from non-volatile memory medium 170. For instance, processor 120 may retrieve executable 173A from non-volatile memory medium 170. In one or more embodiments, DXE 330 may retrieve executable 173A from non-volatile memory medium 170. In one or more embodiments, the first IHS initialization executable/OS executable pair may include IHS initialization executable 173A and OS executable 174A.

At 414, the at least one processor may execute the first IHS initialization executable via an environment associated with the IHSFW. For example, processor 120 may execute IHS initialization executable 173A via an environment associated with IHSFW 172. For instance, the environment associated with IHSFW 172 may include DXE 330. At 416, the first IHS initialization executable may register a subroutine configured to store multiple addresses of a volatile memory medium of the IHS. For example, IHS initialization executable 173A may register subroutine 175, configured to store multiple addresses of volatile memory medium 150.

At 418, the first IHS initialization executable may copy a first OS executable of the first IHS initialization executable/OS executable pair from the first non-volatile memory medium to the volatile memory medium. For example, IHS initialization executable 173A may copy OS executable 174A from non-volatile memory medium 170 to volatile memory medium 150. In one or more embodiments, copying the first OS executable from the first non-volatile memory medium to the volatile memory medium may include retrieving the first OS executable from the volatile memory medium. For example, IHS initialization executable 173A may retrieve OS executable 174A from non-volatile memory medium 170. In one or more embodiments, copying the first OS executable from the first non-volatile memory medium to the volatile memory medium may include writing the first OS executable to the volatile memory medium. For example, IHS initialization executable 173A may write OS executable 174A to volatile memory medium 150.

In one or more embodiments, method elements 420-432 may be performed for each IHS initialization executable/OS executable pair of multiple IHS initialization executable/OS executable pairs. For example, method elements 420-432 may be performed for each IHS initialization executable/OS executable pair of the multiple IHS initialization executable/OS executable pairs 173B/174B-173N/174N.

At 420, an IHS initialization executable of the IHS initialization executable/OS executable pair may be retrieved from the first non-volatile memory medium. For example, an IHS initialization executable 173 of IHS initialization executables 173B-173N may be retrieved from non-volatile memory medium 170. In one instance, IHS initialization executable 173B of IHS initialization executable 173B/OS executable 174B pair may be retrieved from non-volatile memory medium 170. In another instance, IHS initialization executable 173C of IHS initialization executable 173C/OS executable 174C pair may be retrieved from non-volatile memory medium 170.

At 422, the at least one processor may execute the IHS initialization executable via the environment associated with the IHSFW. For example, processor 120 may execute IHS initialization executable 173 of IHS initialization executables 173B-173N via the environment associated with IHSFW 172. In one instance, processor 120 may execute IHS initialization executable 173B via the environment associated with IHSFW 172. In another instance, processor 120 may execute IHS initialization executable 173C via the environment associated with IHSFW 172. In one or more embodiments, the environment associated with IHSFW 172 may include DXE 330.

At 424, the IHS initialization executable may copy an OS executable of the IHS initialization executable/OS executable pair from the first non-volatile memory medium to the volatile memory medium. For example, IHS initialization executable 173 of IHS initialization executables 173B-173N may copy an OS executable 174 of OS executables 174B-174N from non-volatile memory medium 170 to volatile memory medium 150. In one instance, IHS initialization executable 173B may copy OS executable 174B from non-volatile memory medium 170 to volatile memory medium 150. In another instance, IHS initialization executable 173C may copy OS executable 174C from non-volatile memory medium 170 to volatile memory medium 150. In one or more embodiments, copying the OS executable of the IHS initialization executable/OS executable pair from the first non-volatile memory medium to the volatile memory medium may include retrieving the OS executable of the IHS initialization executable/OS executable pair from the first non-volatile memory medium. In one or more embodiments, copying the OS executable of the IHS initialization executable/OS executable pair from the first non-volatile memory medium to the volatile memory medium may include writing the OS executable of the IHS initialization executable/OS executable pair to the volatile memory medium.

At 426, the IHS initialization executable may call the subroutine. For example, IHS initialization executable 173 of IHS initialization executables 173B-173N may call subroutine 175. In one instance, IHS initialization executable 173B may call subroutine 175, as illustrated in FIG. 3B. In another instance, IHS initialization executable 173C may call subroutine 175, as illustrated in FIG. 3C.

At 428, the subroutine may store an address associated with the OS executable via a data structure stored by the volatile memory medium. For example, subroutine 175 may store an address associated with OS executable 174 of OS executables 174B-174N via data structure 176B. In one instance, subroutine 175 may store an address associated with OS executable 174B via data structure 176B. In another instance, subroutine 175 may store an address associated with OS executable 174C via data structure 176B.

At 430, the first OS executable may retrieve the address of the volatile memory medium associated with the OS executable from the data structure. For example, OS executable 174A may retrieve the address of volatile memory medium 150 associated with OS executable 174 of OS executable 174B-174N from data structure 176B. In one instance, OS executable 174A may retrieve address 178B of volatile memory medium 150 associated with OS executable 174B from data structure 176B. In another instance, OS executable 174A may retrieve address 178C of volatile memory medium 150 associated with OS executable 174C from data structure 176B.

At 432, the first OS executable may copy the OS executable from the volatile memory medium to the second non-volatile memory medium based at least on the address of the volatile memory medium associated with the OS executable. For example, OS executable 174A may copy OS executable 174 of OS executable 174B-174N from volatile memory medium 150 to non-volatile memory medium 160 based at least on address 178 associated with OS executable 174 of OS executable 174B-174N. In one instance, OS executable 174A may copy OS executable 174B from volatile memory medium 150 to non-volatile memory medium 160 based at least on address 178B associated with OS executable 174B. In another instance, OS executable 174A may copy OS executable 174C from volatile memory medium 150 to non-volatile memory medium 160 based at least on address 178C associated with OS executable 174C. In one or more embodiments, copying the OS executable from the volatile memory medium to the second non-volatile memory medium based at least on the address of the volatile memory medium associated with the OS executable may include retrieving the OS executable from the volatile memory medium based at least on the address of the volatile memory medium associated with the OS executable. In one or more embodiments, copying the OS executable from the volatile memory medium to the second non-volatile memory medium based at least on the address of the volatile memory medium associated with the OS executable may include writing the OS executable to the second non-volatile memory medium.

At 434, the at least one processor may execute each OS executable of the multiple IHS initialization executable/OS executable pairs via an OS context. For example, processor 120 may execute each OS executable 174 of the multiple IHS initialization executable/OS executable pairs 173B/174B-173N/174N via an OS context. In one or more embodiments, the OS context may include an OS environment. For example, the OS context may include an OS environment (e.g., OS environment 340) of OS 162.

In one or more embodiments, before executing the at least the portion of IHSFW at 410, OS 162 may be installed or reinstalled on the second non-volatile memory medium (e.g., non-volatile memory medium 160), or another operating system, different from OS 162, may be installed on the second non-volatile memory medium. In one example, this may enable each OS executable of the multiple of IHS initialization executable/OS executable pairs to endure on the second non-volatile memory medium. In another example, this may enable each OS executable of the multiple of IHS initialization executable/OS executable pairs to have continuity on the second non-volatile memory medium. In one or more embodiments, each OS executable of the multiple IHS initialization executable/OS executable pairs may endure on the second non-volatile memory medium after another operating system, different from the operating system, has been installed on the second non-volatile memory medium.

Turning now to FIG. 5, an example of utilizing a persistent application that advises how to configure an information handling system is illustrated, according to one or more embodiments. In one or more embodiments, a persistent application 512 may communicate with a persistent settings repository 510. For example, persistent application 512 may communicate with persistent settings repository 510 via a network. In one instance, persistent application 512 may receive configuration information for IHS 110 from persistent settings repository 510 via the network. In a second instance, persistent application 512 may provide configuration information for IHS 110 to persistent settings repository 510 via the network. In another instance, persistent application 512 may provide performance information associated with IHS 110 to persistent settings repository 510 via the network.

In one or more embodiments, persistent application 512 may persist across reboots of IHS 110. In one or more embodiments, persistent application 512 may persist across OS installs on IHS 110. For example, OSE 174B may be or may include persistent application 512. For instance, OSE 174B may persist across reboots of IHS 110 and/or may persist across OS installs on IHS 110.

In one or more embodiments, persistent application 512 may determine information associated with application(s) 514. For example, a registry 516 may store the information associated with application(s) 514. In one instance, persistent application 512 may access registry 516 for the information associated with application(s) 514. In another instance, persistent application 512 may receive the information associated with application(s) 514 from access registry 516. As an example, receiving the information associated with application(s) 514 from access registry 516 may include retrieving the information associated with application(s) 514 from access registry 516.

In one or more embodiments, registry 516 may store a software identification (SWID) tag associated with an application 514. For example, registry 516 may store one or more SWID tags respectively associated with one or more application(s) 514. In one or more embodiments, a SWID tag may include information associated with an application 514. For example, the information associated with an application 514 may include one or more of an identification associated with application 514, a version associated with application 514, and a producer associated with application 514, among others.

In one or more embodiments, IHSFW 172 may include an IHSFW image 534. For example, IHSFW image 534 may include IHSFWV 310. In one or more embodiments, IHSFW image 534 may include ACPI tables 532. For example, ACPI tables 532 may include an ACPI table 530. For instance, ACPI table 530 may include a Windows platform binary table (WPBT). In one or more embodiments, ACPI table 530 may include persistent application 512. For example, when IHS 110 boots, an OS boot loader 522 may receive persistent application 512 from ACPI table 530. In one or more embodiments, an OS kernel mode driver 520 may receive persistent application 512 from OS boot loader 522. For example, OS kernel mode driver 520 may start execution of persistent application 512. In one or more embodiments, persistent application 512 may be or include a foreground application, a background application, or a service (e.g., a Windows service), among others.

Turning now to FIG. 6, an example of a method of operating an information handling system is illustrated, according to one or more embodiments. At 610, an information handling system may boot. For example, IHS 110 may boot. At 612, a WPBT may be loaded by an OS. For instance, OS 162 may load a WPBT. At 614, a service may load. For example, the service may be or may include persistent application 512. For instance, persistent application 512 may be executed via an OS context. As an example, persistent application 512 may be executed via a context of OS 162.

At 616, the service may collect IHS information. In one example, the service may collect system information 650. In one instance, system information 650 may include a service tag associated with IHS 110. In another instance, system information 650 may include an identifier associated with IHS 110. As an example, the identifier associated with IHS 110 may be utilized in determining if IHS 110 is associated with an IHS manufacturer. For instance, an IHS manufacturer may be an OEM such as Dell, Lenovo, Apple, HP, etc. In a second example, the service may collect a power configuration information 652. In one instance, power configuration information 652 may indicate that IHS 110 is in a battery mode (e.g., utilizing battery 130 to provide power to one or more components of IHS 110). In a second instance, power configuration information 652 may indicate that IHS 110 is optimized to utilize a battery (e.g., battery 130). In a third instance, power configuration information 652 may indicate that IHS 110 is optimized for a high performance mode (e.g., in favor of faster processing rather than conserving power or energy). In another instance, power configuration information 652 may indicate that IHS 110 is plugged into a power supply, which may be plugged into a wall socket, an external direct current (DC) power source, etc. In a third example, the service may collect status configuration information 654. In one instance, status configuration information 654 may indicate if a camera (e.g., a web camera) is enabled. In a second instance, status configuration information 654 may indicate a battery age (e.g., an age of battery 130). In a third instance, status configuration information 654 may include information associated with applications installed on IHS 110. In a fourth instance, status configuration information 654 may indicate if a security update may be needed to be installed and/or if a security update is available to be installed. In a fifth instance, status configuration information 654 may indicate if a driver update may be needed to be installed and/or if a driver update is available to be installed. In another instance, status configuration information 654 may include one or more settings stored via non-volatile memory medium 170 (e.g., one or more settings of IHSFW 172, etc.). In a fourth example, the service may collect application information 656. In one instance, application information 656 may include information associated with one or more applications installed on IHS 110. In another instance, application information 656 may include information associated with registry 516.

In another example, the service may collect hardware information 658. In one instance, hardware information 658 may indicate what components of IHS 110 (e.g., processor 120, a graphics processing unit, volatile memory medium 150, non-volatile memory medium 160, non-volatile memory medium 170, I/O subsystem 180, network interface 182, etc.) are installed on IHS 110. In another instance, hardware information 658 may indicate one or more of an operating speed of processor 120, a number of processing cores of processor 120, an operating speed of the graphics processing unit, a number of vectors that the graphics processing unit can simultaneously utilize, an amount of storage of volatile memory medium 150 that is available, and an amount of storage of non-volatile memory medium 160 that is available, among others.

At 618, the service may receive developed configuration information from a cloud repository via a network. For example, the service may receive developed configuration information 662 from a cloud repository via a network 660. For instance, developed configuration information 662 may include best known configuration information. In one or more embodiments, persistent settings repository 510 may store developed configuration information 662. In one example, the service may receive developed configuration information 662 from persistent settings repository 510. In another example, the service may receive developed configuration information 662 from persistent settings repository 510 via network 660.

In one or more embodiments, developed configuration information 662 may include one or more setting that may be utilized by IHS 110 to configure power utilization by IHS 110. In one example, the one or more setting of developed configuration information 662 may include one or more setting recommendations associated with how to configure IHS 110. For instance, the one or more setting of developed configuration information 662 may include one or more setting recommendations associated with how to configure IHS 110 based at least on one or more of system information 650, power configure information 652, status configuration information 654, application information 656, and hardware information 658, among others. In another example, the one or more setting of developed configuration information 662 may include one or more setting recommendations associated with how not to configure IHS 110. For instance, the one or more setting of developed configuration information 662 may include one or more setting recommendations associated with how not to configure IHS 110 based at least on one or more of system information 650, power configure information 652, status configuration information 654, application information 656, and hardware information 658, among others.

In one or more embodiments, developed configuration information 662 may be determined via input from multiple information handling systems (IHSs) 110. For example, the multiple IHSs 110 may provide performance information and/or configuration information to a repository. For instance, each IHS 110 of the multiple IHSs 110 may provide its one or more of system information 650, power configure information 652, status configuration information 654, application information 656, and hardware information 658, among others, and/or its performance information to the repository.

In one or more embodiments, an information handling system associated with the repository (e.g., a cloud repository) may determine one or more setting recommendations associated with how to configure an IHS 110 based at least on the performance information and/or the configuration information from the multiple IHSs 110. For example, a machine learning process or method associated with the repository may determine one or more setting recommendations associated with how to configure an IHS 110 based at least on the performance information and/or the configuration information from the multiple IHSs 110. For instance, a machine learning process or method associated with the repository may determine one or more setting recommendations associated with how to configure a type of IHS 110 based at least on the performance information and/or the configuration information from the multiple IHSs 110.

In one or more embodiments, an information handling system associated with the repository (e.g., a cloud repository) may determine one or more setting recommendations associated with how not to configure an IHS 110 based at least on the performance information and/or the configuration information from the multiple IHSs 110. For instance, a machine learning process or method associated with the repository may determine one or more setting recommendations associated with how not to configure a type of IHS 110 based at least on the performance information and/or the configuration information from the multiple IHSs 110. As an example, a machine learning process or method associated with the repository may determine one or more setting recommendations associated with how not to configure an IHS 110 based at least on the performance information and/or the configuration information from the multiple IHSs 110.

In one or more embodiments, developed configuration information 662 may be determined via a test environment. For example, an OEM may determine developed configuration information 662 via a test environment. In one or more embodiments, developed configuration information 662 may be determined via multiple IHSs 110 associated with a company (e.g., a business entity). For example, an information technology (IT) department of a company may determine, via multiple IHSs 110 associated with the company, developed configuration information 662. For instance, developed configuration information 662 may be specific to the company or may be specific to a department of the company.

At 620, information may be compared. For example, the service may compare developed configuration information 662 with one or more of system information 650, power configure information 652, status configuration information 654, application information 656, and hardware information 658, among others, of IHS 110. For instance, the service may compare one or more of system information 650, power configure information 652, status configuration information 654, application information 656, and hardware information 658, among others, associated with developed configuration information 662 with one or more of system information 650, power configure information 652, status configuration information 654, application information 656, and hardware information 658, among others, associated with IHS 110.

At 622, the service may determine if an update is required. If an update is required, an update of IHS 110 may be performed per a policy, at 624. For example, the service may update one or more power management settings of IHS 110 based at least on a policy. For instance, the policy may be determined based at least on one or more of system information 650, power configure information 652, status configuration information 654, application information 656, and hardware information 658, among others, associated with IHS 110 and based at least on developed configuration information 662. If an update is not required, the method may conclude, at 626.

Turning now to FIGS. 7A and 7B, another example of a method of operating an information handling system is illustrated, according to one or more embodiments. In one or more embodiments, method elements 710-718 may be performed in accordance with method elements 410-418, respectively. At 720, a second IHS initialization executable of a second IHS initialization executable/OS executable pair may be retrieved from the first non-volatile memory medium. For example, IHS initialization executable 173B may be retrieved from non-volatile memory medium 170. At 722, the at least one processor may execute the second IHS initialization executable via the environment associated with the IHSFW. For example, processor 120 may execute IHS initialization executable 173B via the environment associated with IHSFW 172. In one or more embodiments, the environment associated with IHSFW 172 may include DXE 330.

At 724, the second IHS initialization executable may copy a second OS executable of the second IHS initialization executable/OS executable pair from the first non-volatile memory medium to the volatile memory medium. For example, IHS initialization executable 173B may copy OS executable 174B from non-volatile memory medium 170 to volatile memory medium 150. In one or more embodiments, copying the second OS executable of the second IHS initialization executable/OS executable pair from the first non-volatile memory medium to the volatile memory medium may include retrieving the second OS executable of the second IHS initialization executable/OS executable pair from the first non-volatile memory medium. In one or more embodiments, copying the second OS executable of the second IHS initialization executable/OS executable pair from the first non-volatile memory medium to the volatile memory medium may include writing the second OS executable of the second IHS initialization executable/OS executable pair to the volatile memory medium.

At 726, the second IHS initialization executable may call the subroutine. For example, IHS initialization executable 173B may call subroutine 175, as illustrated in FIG. 3B. At 728, the subroutine may store an address associated with the second OS executable via a data structure stored by the volatile memory medium. For example, subroutine 175 may store an address associated with OS executable 174B via data structure 176B. At 730, the first OS executable may retrieve the address of the volatile memory medium associated with the second OS executable from the data structure. For example, OS executable 174A may retrieve the address of volatile memory medium 150 associated with OS executable 174B.

At 732, the first OS executable may copy the second OS executable from the volatile memory medium to the second non-volatile memory medium based at least on the address of the volatile memory medium associated with the second OS executable. For example, OS executable 174A may copy OS executable 174B from volatile memory medium 150 to non-volatile memory medium 160 based at least on address 178B associated with OS executable 174B. In one or more embodiments, copying the second OS executable from the volatile memory medium to the second non-volatile memory medium based at least on the address of the volatile memory medium associated with the second OS executable may include retrieving the second OS executable from the volatile memory medium based at least on the address of the volatile memory medium associated with the second OS executable. In one or more embodiments, copying the second OS executable from the volatile memory medium to the second non-volatile memory medium based at least on the address of the volatile memory medium associated with the second OS executable may include writing the second OS executable to the second non-volatile memory medium.

At 734, the at least one processor may execute the second OS executable via an OS context. For example, processor 120 may execute OS executable 174B via an OS context. In one or more embodiments, the OS context may include an OS environment. For instance, the OS context may include an OS environment (e.g., OS environment 340) of OS 162. In one or more embodiments, before executing the at least the portion of IHSFW at 710, OS 162 may be installed or reinstalled on the second non-volatile memory medium (e.g., non-volatile memory medium 160), or another operating system, different from OS 162, may be installed on the second non-volatile memory medium. In one example, this may enable the second OS executable of the second IHS initialization executable/OS executable pair to endure and/or persist on the second non-volatile memory medium. In another example, this may enable the second OS executable of the second IHS initialization executable/OS executable pair to have continuity and/or persistence on the second non-volatile memory medium. In one or more embodiments, the second OS executable of the second IHS initialization executable/OS executable pair may endure and/or persist on the second non-volatile memory medium after another operating system, different from the operating system, has been installed on the second non-volatile memory medium.

At 736, the second OS executable may determine that at least one application, executable via the OS context, has been installed on the IHS in addition to multiple applications, executable via the OS context, that have already been installed on the IHS. For example, OS executable 174B may determine that at least one application, executable via the OS context, has been installed on the IHS in addition to multiple applications, executable via the OS context, that have already been installed on the IHS. At 738, the second OS executable may determine information associated with the at least one application and at least one of system information associated with the IHS, power configuration information associated with the IHS, status configuration information associated with the IHS, and hardware information associated with the IHS. For example, OS executable 174B may determine information associated with the at least one application and at least one of system information associated with the IHS, power configuration information associated with the IHS, status configuration information associated with the IHS, and hardware information associated with the IHS.

In one or more embodiments, the second OS executable may determine the information associated with the at least one application and at least one of the system information associated with the IHS, the power configuration information associated with the IHS, the status configuration information associated with the IHS, and the hardware information associated with the IHS in response to determining that the at least one application has been installed on the IHS. In one instance, the system information associated with the IHS may include at least one of a service tag associated with the IHS and an identifier associated with the IHS, among others. In a second instance, the power configuration information associated with the IHS may indicate at least one of that the IHS is in a battery mode, that the IHS is optimized to utilize a battery, that the IHS is optimized for a high performance mode, and that the IHS is plugged into a power supply, among others. In a third instance, the configuration information may indicate at least on of whether or not an internal camera is enabled and at least one setting of the IHSFW, among others. In another instance, the hardware information associated with the IHS may include at least one of an operating speed of the at least one processor, a number of processing cores of the at least one processor, an operating speed of a graphics processing unit, a number of vectors that the graphics processing unit can simultaneously utilize, an amount of random access memory that the IHS includes, and an amount of storage of non-volatile memory medium 160 is available, among others.

At 740, the second OS executable may receive developed configuration information via a network. For example, OS executable 174B may receive developed configuration information 662 via network 660. For instance, OS executable 174B may receive developed configuration information 662 from persistent settings repository 510 via network 660.

At 742, the second OS executable may provide first information that recommends how to configure power utilization of the IHS and second information that recommends how not to configure power utilization of the IHS based at least on the developed configuration information, based at least on the information associated with the at least one application, and based at least on the at least one of system information associated with the IHS, power configuration information associated with the IHS, configuration information associated with the IHS, and hardware information associated with the IHS. For example, OS executable 174B may provide first information that recommends how to configure power utilization of IHS 110 and second information that recommends how not to configure power utilization of IHS 110 based at least on developed configuration information 662, based at least on the information associated with the at least one application, and based at least on the at least one of system information 650 associated with IHS 110, power configuration information 652 associated with IHS 110, status configuration information 654 associated with IHS 110, and hardware information 658 associated with IHS 110. For instance, the information associated with the at least one application may include application information 656.

In one or more embodiments, providing the first information that recommends how to configure power utilization of the IHS and the second information that recommends how not to configure power utilization of the IHS may include providing, to a user, the first information that recommends how to configure power utilization of the IHS and the second information that recommends how not to configure power utilization of the IHS to a user via a user interface. For example, the user interface may include a graphical user interface. In one or more embodiments, the user interface may provide a user with an opportunity to revert to any previous configuration of IHS 110. In one or more embodiments, the user interface may provide a user with an opportunity to revert to any configuration received via a network (e.g., network 660). In one example, the user interface may provide a user with an opportunity to revert to any configuration received from persistent settings repository 510. In another example, the user interface may provide a user with an opportunity to revert to any configuration received from an OEM.

In one or more embodiments, one or more of the method and/or process elements and/or one or more portions of a method and/or a process element may be performed in varying orders, may be repeated, or may be omitted. Furthermore, additional, supplementary, and/or duplicated method and/or process elements may be implemented, instantiated, and/or performed as desired, according to one or more embodiments. Moreover, one or more of system elements may be omitted and/or additional system elements may be added as desired, according to one or more embodiments.

In one or more embodiments, a memory medium may be and/or may include an article of manufacture. For example, the article of manufacture may include and/or may be a software product and/or a program product. For instance, the memory medium may be coded and/or encoded with processor-executable instructions in accordance with at least a portion of one or more flowcharts, at least a portion of one or more systems, at least a portion of one or more methods, and/or at least a portion of one or more processes described herein to produce the article of manufacture.

The above disclosed subject matter is to be considered illustrative, and not restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments which fall within the true spirit and scope of the present disclosure. Thus, to the maximum extent allowed by law, the scope of the present disclosure is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited by the foregoing detailed description. 

What is claimed is:
 1. An information handling system, comprising: at least one processor; and a memory medium, coupled to the at least one processor, that stores instructions executable by the at least one processor, which when executed by the at least one processor, cause the information handling system to: execute, by the at least one processor, at least a portion of information handling system firmware (IHSFW) from a first non-volatile memory medium of the information handling system (IHS); retrieve, from the first non-volatile memory medium, a first IHS initialization executable of a first IHS initialization executable/operating system (OS) executable pair; execute, by the at least one processor, the first IHS initialization executable via an environment associated with the IHSFW; retrieve, from the first non-volatile memory medium, a second IHS initialization executable of a second IHS initialization executable/OS executable pair; execute, by the at least one processor, the second IHS initialization executable via the environment associated with the IHSFW; execute, by the at least one processor, a second OS executable of the second IHS initialization executable/OS executable pair via an OS context of an OS; determine, by the second OS executable, that at least one application, executable via the OS context, has been installed on the IHS in addition to a plurality of applications, executable via the OS context, that have already been installed on the IHS; in response to determining that the at least one application has been installed on the IHS, determine, by the second OS executable, information associated with the at least one application and at least one of system information associated with the IHS, power configuration information associated with the IHS, status configuration information associated with the IHS, and hardware information associated with the IHS; receive, by the second OS executable, developed configuration information via a network; provide, by the second OS executable, first information that recommends how to configure power utilization of the IHS and second information that recommends how not to configure power utilization of the IHS based at least on the developed configuration information, based at least on the information associated with the at least one application, and based at least on the at least one of system information associated with the IHS, power configuration information associated with the IHS, configuration information associated with the IHS, and hardware information associated with the IHS.
 2. The information handling system of claim 1, wherein the instructions further cause the information handling system to: register, by the first IHS initialization executable, a subroutine configured to store a plurality of addresses of a volatile memory medium of the IHS; copy, by the first IHS initialization executable, the first OS executable of the first IHS initialization executable/OS executable pair from the first non-volatile memory medium to the volatile memory medium; copy, by the second IHS initialization executable, the second OS executable from the first non-volatile memory medium to the volatile memory medium; call, by the second IHS initialization executable, the subroutine; store, by the subroutine, an address associated with the second OS executable via a data structure stored by the volatile memory medium; retrieve, by the first OS executable, the address of the volatile memory medium associated with the second OS executable from the data structure; and copy, by the first OS executable, the second OS executable from the volatile memory medium to the second non-volatile memory medium based at least on the second address of the volatile memory medium associated with the second OS executable.
 3. The information handling system of claim 2, wherein the data structure includes a table that is compliant with an Advanced Configuration and Power Interface (ACPI) table.
 4. The information handling system of claim 1, wherein the system information associated with the IHS includes at least one of a service tag associated with the IHS and an identifier associated with the IHS.
 5. The information handling system of claim 1, wherein the power configuration information associated with the IHS indicates at least one of that the IHS is in a battery mode, that the IHS is optimized to utilize a battery, that the IHS is optimized for a high performance mode, and that the IHS is plugged into a power supply.
 6. The information handling system of claim 1, wherein the configuration information indicates at least on of whether or not an internal camera is enabled, and at least one setting of the IHSFW.
 7. The information handling system of claim 1, wherein the hardware information associated with the IHS includes at least one of an operating speed of the at least one processor, a number of processing cores of the at least one processor, an operating speed of a graphics processing unit, a number of vectors that the graphics processing unit can simultaneously utilize, an amount of random access memory that the IHS includes, and an amount of storage of the second non-volatile memory medium available.
 8. A method, comprising: executing, by at least one processor of an information handling system (IHS), at least a portion of IHS firmware (IHSFW) from a first non-volatile memory medium of the IHS; retrieving, from the first non-volatile memory medium, a first IHS initialization executable of a first IHS initialization executable/operating system (OS) executable pair; executing, by the at least one processor, the first IHS initialization executable via an environment associated with the IHSFW; retrieving, from the first non-volatile memory medium, a second IHS initialization executable of a second IHS initialization executable/OS executable pair; executing, by the at least one processor, the second IHS initialization executable via the environment associated with the IHSFW; executing, by the at least one processor, a second OS executable of the second IHS initialization executable/OS executable pair via an OS context of an operating system; determining, by the second OS executable, that at least one application, executable via the OS context, has been installed on the IHS in addition to a plurality of applications, executable via the OS context, that have already been installed on the IHS; in response to the determining that the at least one application has been installed on the IHS, determining, by the second OS executable, information associated with the at least one application and at least one of system information associated with the IHS, power configuration information associated with the IHS, status configuration information associated with the IHS, and hardware information associated with the IHS; receiving, by the second OS executable, developed configuration information via a network; providing, by the second OS executable, first information that recommends how to configure power utilization of the IHS and second information that recommends how not to configure power utilization of the IHS based at least on the developed configuration information, based at least on the information associated with the at least one application, and based at least on the at least one of system information associated with the IHS, power configuration information associated with the IHS, configuration information associated with the IHS, and hardware information associated with the IHS.
 9. The method of claim 8, further comprising: registering, by the first IHS initialization executable, a subroutine configured to store a plurality of addresses of a volatile memory medium of the IHS; copying, by the first IHS initialization executable, the first OS executable of the first IHS initialization executable/OS executable pair from the first non-volatile memory medium to the volatile memory medium; copying, by the second IHS initialization executable, the second OS executable from the first non-volatile memory medium to the volatile memory medium; calling, by the second IHS initialization executable, the subroutine; storing, by the subroutine, an address associated with the second OS executable via a data structure stored by the volatile memory medium; retrieving, by the first OS executable, the address of the volatile memory medium associated with the second OS executable from the data structure; and copying, by the first OS executable, the second OS executable from the volatile memory medium to the second non-volatile memory medium based at least on the second address of the volatile memory medium associated with the second OS executable.
 10. The method of claim 9, wherein the data structure includes a table that is compliant with an Advanced Configuration and Power Interface (ACPI) table.
 11. The method of claim 8, wherein the system information associated with the IHS includes at least one of a service tag associated with the IHS and an identifier associated with the IHS.
 12. The method of claim 8, wherein the power configuration information associated with the IHS indicates at least one of that the IHS is in a battery mode, that the IHS is optimized to utilize a battery, that the IHS is optimized for a high performance mode, and that the IHS is plugged into a power supply.
 13. The method of claim 8, wherein the configuration information indicates at least on of whether or not an internal camera is enabled, and at least one setting of the IHSFW.
 14. The method of claim 8, wherein the hardware information associated with the IHS includes at least one of an operating speed of the at least one processor, a number of processing cores of the at least one processor, an operating speed of a graphics processing unit, a number of vectors that the graphics processing unit can simultaneously utilize, an amount of random access memory that the IHS includes, and an amount of storage of the second non-volatile memory medium available.
 15. A computer-readable non-transitory memory medium that includes instructions that, when executed by at least one processor of an information handling system, cause the information handling system to: execute, by the at least one processor, at least a portion of information handling system firmware (IHSFW) from a first non-volatile memory medium of the information handling system (IRS); retrieve, from the first non-volatile memory medium, a first IHS initialization executable of a first IHS initialization executable/operating system (OS) executable pair; execute, by the at least one processor, the first IHS initialization executable via an environment associated with the IHSFW; retrieve, from the first non-volatile memory medium, a second IHS initialization executable of a second IHS initialization executable/OS executable pair; execute, by the at least one processor, the second IHS initialization executable via the environment associated with the IHSFW; execute, by the at least one processor, a second OS executable of the second IHS initialization executable/OS executable pair via an OS context of an operating system; determine, by the second OS executable, that at least one application, executable via the OS context, has been installed on the IHS in addition to a plurality of applications, executable via the OS context, that have already been installed on the IHS; in response to determining that the at least one application has been installed on the IHS, determine, by the second OS executable, information associated with the at least one application and at least one of system information associated with the IHS, power configuration information associated with the IHS, status configuration information associated with the IHS, and hardware information associated with the IHS; receive, by the second OS executable, developed configuration information via a network; provide, by the second OS executable, first information that recommends how to configure power utilization of the IHS and second information that recommends how not to configure power utilization of the IHS based at least on the developed configuration information, based at least on the information associated with the at least one application, and based at least on the at least one of system information associated with the IHS, power configuration information associated with the IHS, configuration information associated with the IHS, and hardware information associated with the IHS.
 16. The computer-readable non-transitory memory medium of claim 15, wherein the instructions further cause the information handling system to: register, by the first IHS initialization executable, a subroutine configured to store a plurality of addresses of a volatile memory medium of the IHS; copy, by the first IHS initialization executable, the first OS executable of the first IHS initialization executable/OS executable pair from the first non-volatile memory medium to the volatile memory medium; copy, by the second IHS initialization executable, the second OS executable from the first non-volatile memory medium to the volatile memory medium; call, by the second IHS initialization executable, the subroutine; store, by the subroutine, an address associated with the second OS executable via a data structure stored by the volatile memory medium; retrieve, by the first OS executable, the address of the volatile memory medium associated with the second OS executable from the data structure; and copy, by the first OS executable, the second OS executable from the volatile memory medium to the second non-volatile memory medium based at least on the second address of the volatile memory medium associated with the second OS executable.
 17. The computer-readable non-transitory memory medium of claim 15, wherein the system information associated with the IHS includes at least one of a service tag associated with the IHS and an identifier associated with the IHS.
 18. The computer-readable non-transitory memory medium of claim 15, wherein the power configuration information associated with the IHS indicates at least one of that the IHS is in a battery mode, that the IHS is optimized to utilize a battery, that the IHS is optimized for a high performance mode, and that the IHS is plugged into a power supply.
 19. The computer-readable non-transitory memory medium of claim 15, wherein the configuration information indicates at least on of whether or not an internal camera is enabled, and at least one setting of the IHSFW.
 20. The computer-readable non-transitory memory medium of claim 15, wherein the hardware information associated with the IHS includes at least one of an operating speed of the at least one processor, a number of processing cores of the at least one processor, an operating speed of a graphics processing unit, a number of vectors that the graphics processing unit can simultaneously utilize, an amount of random access memory that the IHS includes, and an amount of storage of the second non-volatile memory medium available. 